Distributed-Pair Programming can work well and is not just Distributed Pair-Programming

Background: Distributed Pair Programming can be performed via screensharing or via a distributed IDE. The latter offers the freedom of concurrent editing (which may be helpful or damaging) and has even more awareness deficits than screen sharing. Objective: Characterize how competent distributed pair programmers may handle this additional freedom and these additional awareness deficits and characterize the impacts on the pair programming process. Method: A revelatory case study, based on direct observation of a single, highly competent distributed pair of industrial software developers during a 3-day collaboration. We use recordings of these sessions and conceptualize the phenomena seen. Results: 1. Skilled pairs may bridge the awareness deficits without visible obstruction of the overall process. 2. Skilled pairs may use the additional editing freedom in a useful limited fashion, resulting in potentially better fluency of the process than local pair programming. Conclusion: When applied skillfully in an appropriate context, distributed-pair programming can (not will!) work at least as well as local pair programming

Understanding Tools and Practices for Distributed Pair Programming

When considering the principles for eXtreme Programming, distributed eXtreme Programming, especially distributed pair programming, is a paradox predetermined to failure. However, global software development as well as the outsourcing of software development are integral parts of software projects. Hence, the support for distributed pair programming is still a challenging field for tool developers so that failure for distributed pair programming becomes less mandatory. In this paper, we analyse the social interaction in distributed pair programming and investigate how current technology supports this interaction. We present XPairtise, a plug-in for Eclipse that allows instant pair programming in distributed development teams. In addition, we report on experiences and findings when using XPairtise in a distributed software development setting.Mullti Actor SystemsTechnology, Policy and Managemen